I continue to wait patiently for Pycom to support its product it sold me.

@nwjlyons It improved drastically, from 17 hours to 2-3 days. Definitely use deepsleep!

@hanssanitizer Leaving the LoRa radio in RX mode means the LoRa chip will be drawing a bit over 10 mA at all times. What are your constraints in terms of battery size and battery lifetime? A relatively large 2500 mAh will be emptied in 10 days in this scheme, not even counting what is drawn when the LoPy is awake, so probably less than a week overall, depending on how often it wakes up, for how long, and what it does. If that's something that is acceptable for you, then one could probably explore modifying the firmware to handle that, though my guess the complexity will arise from having to bypass all the LoRa chip initialisation on startup. Note that if that kind of power budget is acceptable, maybe just using the light sleep modes may be OK and probably much easier. For reference, the original LoPy uses the SX1272 while the LoPy4 uses the SX1276. I believe the FiPy uses the SX1276 as well.

To anyone using the Bell Canada LTE Cat M1 network: just got word from them and it seems that at this point there is PSM support but: "eDRX feature is under consideration for future availability but there is no announced plan yet". I'll be playing with the +CPSMS AT command to see what's possible.

@jardar I had the same question today. (Funny coincidence.) I found this by searching the forum: "The only optimisation at the moment is enabling WLAN Power Saving in STA mode (basically the WiFi radio only 'wakes up' at the beacon interval set by your gateway) so you'll see current go down to about 50mA and then 100+ mA at the wake intervals. This is done by re-initilizating WLAN with power_save=True option. However it's not perfect yet, it may caused network timeouts for some people so it became disabled again by default." (Source)

@jmarcelino I've tested this now (removed lte = LTE() and lte.deinit() ) and the peak is still there. The device goes into deep sleep, but like before the current rises quickly to about 200 mA for a couple of seconds before it goes into deep sleep. I also find it strange that it doesn't happen the first time the device goes into deep sleep, but all consecutive runs. The first time now, since I don't deinit() LTE the current is at about 200 mA and drops down to deep sleep. Then when waking up it is around 60-70 mA when measuring and then peaks to 200 right before deep sleep.

@robert-hh I have the same impression. I had a 15 minutes deep sleep cycle running the night and the time was ~4 minutes off in the morning.

@toppert Some of power banks can support low current mode. Some of tem must be turned in this mode by special press on the button, some work from the start. But many do not support low current mode at all. E.g. "Mi" power banks support this mode - but as @seb say already it is super inefficient. You can got longer time from battery then from powerbanks.

@daniel Would the LoRa chip on a LoPy stay active during light sleep? If so, the same kind of trick could help save quite a bit of energy when sending a packet: the time until RX2 usually does not need the CPU to be doing anything, so one could easily save 2 seconds of CPU awake time. When using the slowest data rates, the CPU could also be sleeping during the TX phase itself, I suppose. Even if light sleep is not possible, what about machine.idle? I understand it’s not currently working as intended, but if there’s a way to fix that it could probably help as well.

You can get the wake reason using ds.get_wake_status(). I think the default is that there are no other wake-up sources configured, but you may try to disable_wake_on_fall(['P10','P17', 'P18']) and disable_wake_on_raise(['P10','P17', 'P18']) just to be sure. Full details here: https://docs.pycom.io/chapter/datasheets/boards/deepsleep/api.html

I suffer the same error with the new firmware version (1.10.2.b1). It seems they have not solved it until now... Have you found any solution?+ Thanks

Any news on the ability to utilize the ULP through micropython APIs?

@chrisi Are you measuring over USB or on a battery? According to this post: https://forum.pycom.io/topic/1460/power-consumption-deep-sleep-pysense-pytrack/20 you'll get about 10 mA more over USB. Also, are you using the expansion board, Pysense, Pytrack...?

@chrisi Or what about good old UART?

@asaph I've tried it out and it works fantastically 🎉 Thanks @Daniel!

@jmarcelino said in CPU Frequency: I changed it, but got the same results. Mike

@lebucur The Lopy warms up a little bit when running. Can you estimate how worm it get's. It's normal that it gets a little bit warmer than environmental temperature, so it feels warm, but you should still be able to touch it without without any pain. Is it the deviec in total or a specific component?